Mobile-based cartographic control of display content

ABSTRACT

A content display system can control which content and how the content is displayed based on viewing parameters, such as a map zoom level, and physical distance parameters, e.g., a geo-fence distance and an icon visibility distance. Different combinations of input (e.g., zoom level and physical distances) yield a myriad of pre-set content displays on the client device, thereby allowing a creator of an icon to finely tune how content displayed otherwise accessed.

PRIORITY CLAIM

This application a continuation of and claims the benefit of priority ofU.S. patent application Ser. No. 15/797,859, filed Oct. 30, 2017, whichis hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure generally relates to machines special-purposemachines that manage display of user interface content and improvementsto such variants, and to the technologies by which such special-purposemachines become improved compared to other special-purpose machines formobile-based cartographic control of content.

BACKGROUND

A user can view a map showing his or her location and surrounding areaon a client device (e.g., a smartphone). While maps can be shown onclient devices, granular control of which content and how the content isdisplayed is difficult due to limitations of the client device (e.g.,screen size, memory limitations, network bandwidth limitations, and lackof input/output controls and interfaces).

BRIEF DESCRIPTION OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure (“FIG.”) number in which that element or act is first introduced.

FIG. 1 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a network.

FIG. 2 is a block diagram illustrating further details regarding themessaging system of FIG. 1, according to example embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored in adatabase of a messaging server system, according to certain exampleembodiments.

FIG. 4 is a schematic diagram illustrating a structure of a message,according to some embodiments, generated by a messaging clientapplication for communication.

FIG. 5 is a schematic diagram illustrating an example access-limitingprocess, in terms of which access to content (e.g., an ephemeralmessage, and associated multimedia payload of data) or a contentcollection (e.g., an ephemeral message story) may be time-limited (e.g.,made ephemeral), according to some example embodiments.

FIG. 6 shows example internal functional components of a cartographiccontent display system, according to some example embodiments.

FIG. 7 shows an example flow diagram of a method for implementinggeo-parameter based content distribution, according to some exampleembodiments.

FIG. 8 shows an example finite state machine (FSM) architecture forconfiguration of an icon engine based on icon settings, according tosome example embodiments.

FIG. 9 shows example icon settings, according to some exampleembodiments.

FIGS. 10A-D show example user interfaces implementing icon and overlaycontent, according to some example embodiments.

FIGS. 11A and 11B show example map zoom levels, according to someexample embodiments.

FIG. 12 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described.

FIG. 13 is a block diagram illustrating components of a machine,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

As discussed, granular control of content on client devices isdifficult. To this end, a cartographic content display system can morefinely control which content and how the content is displayed on aclient device based on viewing parameters (e.g., a map zoom level), andphysical distance parameters (e.g., how close the client device is to apre-specified target coordinate). In some implementations, physicaldistance is distance from a client device to an icon which has beenplaced at a target coordinate on a map. The physical distance parametersfor a given icon may comprise two different and independent values: ageo-fence distance operable to unlock content, and an icon visibilitydistance operable to display the given icon on a map. Differentcombinations of input (e.g., zoom level and physical distances) yield amyriad of pre-set content display scenarios, thereby, allowing a creatorof an icon to more finely tune how content displayed with the icon isunlocked or otherwise accessed.

FIG. 1 shows a block diagram of an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network106. The messaging system 100 includes multiple client devices 102, eachof which hosts a number of applications including a messaging clientapplication 104. Each messaging client application 104 iscommunicatively coupled to other instances of the messaging clientapplication 104 and a messaging server system 108 via the network 106(e.g., the Internet).

Accordingly, each messaging client application 104 is able tocommunicate and exchange data with another messaging client application104 and with the messaging server system 108 via the network 106. Thedata exchanged between messaging client applications 104, and between amessaging client application 104 and the messaging server system 108,includes functions (e.g., commands to invoke functions) as well aspayload data (e.g., text, audio, video, or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, it will be appreciated that the location ofcertain functionality within either the messaging client application 104or the messaging server system 108 is a design choice. For example, itmay be technically preferable to initially deploy certain technology andfunctionality within the messaging server system 108, and to latermigrate this technology and functionality to the messaging clientapplication 104 where a client device 102 has a sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include message content, client device information, geolocationinformation, media annotation and overlays, message content persistenceconditions, social network information, and live event information, asexamples. Data exchanges within the messaging system 100 are invoked andcontrolled through functions available via user interfaces (UIs) of themessaging client application 104.

Turning now specifically to the messaging server system 108, anapplication programming interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

The API server 110 receives and transmits message data (e.g., commandsand message payloads) between the client devices 102 and the applicationserver 112. Specifically, the API server 110 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client application 104 in order to invoke functionalityof the application server 112. The API server 110 exposes variousfunctions supported by the application server 112, including accountregistration; login functionality; the sending of messages, via theapplication server 112, from a particular messaging client application104 to another messaging client application 104; the sending of mediafiles (e.g., images or video) from a messaging client application 104 toa messaging server application 114 for possible access by anothermessaging client application 104; the setting of a collection of mediadata (e.g., a story); the retrieval of such collections; the retrievalof a list of friends of a user of a client device 102; the retrieval ofmessages and content; the adding and deletion of friends to and from asocial graph; the location of friends within the social graph; andopening application events (e.g., relating to the messaging clientapplication 104).

The application server 112 hosts a number of applications andsubsystems, including the messaging server application 114, an imageprocessing system 116, a social network system 122, and an icon system150. The messaging server application 114 implements a number ofmessage-processing technologies and functions, particularly related tothe aggregation and other processing of content (e.g., textual andmultimedia content) included in messages received from multipleinstances of the messaging client application 104. As will be describedin further detail, the text and media content from multiple sources maybe aggregated into collections of content (e.g., called stories orgalleries). These collections are then made available, by the messagingserver application 114, to the messaging client application 104. Otherprocessor- and memory-intensive processing of data may also be performedserver-side by the messaging server application 114, in view of thehardware requirements for such processing.

The application server 112 also includes the image processing system116, which is dedicated to performing various image processingoperations, typically with respect to images or video received withinthe payload of a message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions and services, and makes these functions and services availableto the messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph (e.g., entity graph304 in FIG. 3) within the database 120. Examples of functions andservices supported by the social network system 122 include theidentification of other users of the messaging system 100 with whom aparticular user has relationships or whom the particular user is“following,” and also the identification of other entities and interestsof a particular user.

The icon system 150 is configured to interface with a cartographiccontent display system 210 (described below with reference to FIG. 2)via the network 106. The icon system 150 can receive location data for aclient device 102 and return, to the client device 102, a set of nearbyicons (e.g., nearby icon metadata). Further, the icon system 150 cansend, to the client device 102, content associated with an icon (e.g.,upon the icon content being unlocked).

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

FIG. 2 is a block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of subsystems, namely an ephemeral timer system 202, a collectionmanagement system 204, an annotation system 206, and a cartographiccontent display system 210.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message orcollection of messages (e.g., a SNAPCHAT Story), selectively display andenable access to messages and associated content via the messagingclient application 104. Further details regarding the operation of theephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image, video, and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text, and audio) may be organized into an“event gallery” or an “event story.” Such a collection may be madeavailable for a specified time period, such as the duration of an eventto which the content relates. For example, content relating to a musicconcert may be made available as a “story” for the duration of thatmusic concert. The collection management system 204 may also beresponsible for publishing an icon that provides notification of theexistence of a particular collection to the user interface of themessaging client application 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion ofuser-generated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay (e.g., a SNAPCHAT Geofilter orfilter) to the messaging client application 104 based on a geolocationof the client device 102. In another example, the annotation system 206operatively supplies a media overlay to the messaging client application104 based on other information, such as social network information ofthe user of the client device 102. A media overlay may include audio andvisual content and visual effects. Examples of audio and visual contentinclude pictures, text, logos, animations, and sound effects. An exampleof a visual effect includes color overlaying. The audio and visualcontent or the visual effects can be applied to a media content item(e.g., a photo) at the client device 102. For example, the media overlayincludes text that can be overlaid on top of a photograph generated bythe client device 102. In another example, the media overlay includes anidentification of a location (e.g., Venice Beach), a name of a liveevent, or a name of a merchant (e.g., Beach Coffee House). In anotherexample, the annotation system 206 uses the geolocation of the clientdevice 102 to identify a media overlay that includes the name of amerchant at the geolocation of the client device 102. The media overlaymay include other indicia associated with the merchant. The mediaoverlays may be stored in the database 120 and accessed through thedatabase server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map and upload content associated with the selectedgeolocation. The user may also specify circumstances under whichparticular content should be offered to other users. The annotationsystem 206 generates a media overlay that includes the uploaded contentand associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest-bidding merchant with a corresponding geolocationfor a predefined amount of time.

As discussed in further detail below, the cartographic content displaysystem 210 is configured to display icon and icon content based ondisplay setting and location data of a client device 102.

FIG. 3 is a schematic diagram illustrating data 300 which may be storedin the database 120 of the messaging server system 108, according tocertain example embodiments. While the content of the database 120 isshown to comprise a number of tables, it will be appreciated that thedata 300 could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table314. An entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events, and so forth. Regardless of type, any entity regardingwhich the messaging server system 108 stores data may be a recognizedentity. Each entity is provided with a unique identifier, as well as anentity type identifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between or among entities. Suchrelationships may be social, professional (e.g., work at a commoncorporation or organization), interest-based, or activity-based, forexample.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of varioustypes, including user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters), which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a Global Positioning System(GPS) unit of the client device 102. Another type of filter is a datafilter, which may be selectively presented to a sending user by themessaging client application 104, based on other inputs or informationgathered by the client device 102 during the message creation process.Examples of data filters include a current temperature at a specificlocation, a current speed at which a sending user is traveling, abattery life for a client device 102, or the current time.

Other annotation data that may be stored within the image table 308 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe message table 314. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a SNAPCHAT Story or a gallery). The creation of aparticular collection may be initiated by a particular user (e.g., eachuser for whom a record is maintained in the entity table 302). A usermay create a “personal story” in the form of a collection of contentthat has been created and sent/broadcast by that user. To this end, theuser interface of the messaging client application 104 may include anicon that is user-selectable to enable a sending user to add specificcontent to his or her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom various locations and events. Users whose client devices 102 havelocation services enabled and are at a common location or event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104 based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 400 is used to populate the message table 314stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 400 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 400 is shown to include thefollowing components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 102 and that is included        in the message 400.    -   A message image payload 406: image data captured by a camera        component of a client device 102 or retrieved from memory of a        client device 102, and that is included in the message 400.    -   A message video payload 408: video data captured by a camera        component or retrieved from a memory component of the client        device 102, and that is included in the message 400.    -   A message audio payload 410: audio data captured by a microphone        or retrieved from the memory component of the client device 102,        and that is included in the message 400.    -   Message annotations 412: annotation data (e.g., filters,        stickers, or other enhancements) that represents annotations to        be applied to the message image payload 406, message video        payload 408, or message audio payload 410 of the message 400.    -   A message duration parameter 414: a parameter value indicating,        in seconds, the amount of time for which content of the message        400 (e.g., the message image payload 406, message video payload        408, and message audio payload 410) is to be presented or made        accessible to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message 400. Multiple message geolocation        parameter 416 values may be included in the payload, with each        of these parameter values being associated with respective        content items included in the content (e.g., a specific image in        the message image payload 406, or a specific video in the        message video payload 408).    -   A message story identifier 418: values identifying one or more        content collections (e.g., “stories”) with which a particular        content item in the message image payload 406 of the message 400        is associated. For example, multiple images within the message        image payload 406 may each be associated with multiple content        collections using identifier values.    -   A message tag 420: one or more tags, each of which is indicative        of the subject matter of content included in the message        payload. For example, where a particular image included in the        message image payload 406 depicts an animal (e.g., a lion), a        tag value may be included within the message tag 420 that is        indicative of the relevant animal. Tag values may be generated        manually, based on user input, or may be automatically generated        using, for example, image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 on        which the message 400 was generated and from which the message        400 was sent.    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The contents (e.g., values) of the various components of the message 400may be pointers to locations in tables within which content data valuesare stored. For example, an image value in the message image payload 406may be a pointer to (or address of) a location within the image table308. Similarly, values within the message video payload 408 may point todata stored within the video table 310, values stored within the messageannotations 412 may point to data stored in the annotation table 312,values stored within the message story identifier 418 may point to datastored in the story table 306, and values stored within the messagesender identifier 422 and the message receiver identifier 424 may pointto user records stored within the entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message story 504) may be time-limited (e.g., madeephemeral), according to some example embodiments.

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client application 104. Inone embodiment, where the messaging client application 104 is a SNAPCHATapplication client, an ephemeral message 502 is viewable by a receivinguser for up to a maximum of 10 seconds, depending on the amount of timethat the sending user specifies using the message duration parameter506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of contentan ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message story 504 (e.g., a personal SNAPCHAT Story, or anevent story). The ephemeral message story 504 has an associated storyduration parameter 508, a value of which determines a time duration forwhich the ephemeral message story 504 is presented and accessible tousers of the messaging system 100. The story duration parameter 508, forexample, may be the duration of a music concert, where the ephemeralmessage story 504 is a collection of content pertaining to that concert.Alternatively, a user (either the owning user or a curator user) mayspecify the value for the story duration parameter 508 when performingthe setup and creation of the ephemeral message story 504.

Additionally, each ephemeral message 502 within the ephemeral messagestory 504 has an associated story participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message story504. Accordingly, a particular ephemeral message 502 may “expire” andbecome inaccessible within the context of the ephemeral message story504, prior to the ephemeral message story 504 itself expiring in termsof the story duration parameter 508.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message story 504based on a determination that it has exceeded an associated storyparticipation parameter 510. For example, when a sending user hasestablished a story participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message story 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message story 504 either when the storyparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message story 504 has expired, or when theephemeral message story 504 itself has expired in terms of the storyduration parameter 508.

In response to the ephemeral timer system 202 determining that anephemeral message story 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (e.g., specifically, the messaging client application 104) to causean indicium (e.g., an icon) associated with the relevant ephemeralmessage story 504 to no longer be displayed within a user interface ofthe messaging client application 104.

FIG. 6 shows example internal functional components of a cartographiccontent display system 210, according to some example embodiments. Asillustrated, the cartographic content display system 210 comprises a mapengine 605, a geolocation engine 610, an icon engine 615, a contentengine 620, and an interface engine 625. The map engine 605 isconfigured to display a map based on where the client device 102 isphysically located. Further, according to some embodiments, the mapengine 605 is configured to display an icon for unlockable overlaycontent based on parameters received from the icon engine 615 beingsatisfied (e.g., a zoom level, a pre-specified geo-fence distance,and/or a pre-specified icon visibility distance being met). Thegeolocation engine 610 is configured to determine the physicalgeographic location of the client device 102 using a network sensor,such as a GPS sensor or Internet network sensor. In the embodiments inwhich a GPS sensor is used, the location of the client device 102 can belatitude and longitude coordinates that are determined by accessing oneor more wireless networks radiating from GPS satellites, as known to oneof ordinary skill in the art. In the embodiments in which thegeolocation engine (310 uses an Internet sensor (e.g., a Wi-Fi sensor)to determine location (e.g., a WiFi network), the Internet sensordetects an. Internet Protocol (IP) network and can determine locationinformation such as venue location or country information. In someexample embodiments, the detected IP networks have addresses thatcorrespond to known locations. For example, if an IP network of a city'sWiMAX is detected (e.g., San Jose, Calif.'s, city-wide “Wickedly FastWi-Fi” network, a coffee shop's Wi-Fi), the geolocation engine 610 thendetermines that the client device 102 is located in the given city(e.g., San Jose, Calif.) or around the given venue (e.g., the coffeeshop).

The icon engine 615 is configured to determine whether one or moreparameters are satisfied for showing an icon and unlocking overlaycontent. For example, the icon engine 615 can determine whether apre-specified geo-fence distance is satisfied, a pre-specified iconvisibility distance is satisfied, and the zoom level setting issatisfied, as discussed in further detail below.

The content engine 620 is configured to display content unlocked basedon the icon settings. Further, according to some example embodiments,the content engine 620 is further configured to generate an image of theunlocked content overlaid on an image captured using an image sensor ofthe client device 102. Further, according to some example embodiments,the content engine 620 is configured to interface with the annotationsystem 206 to overlay additional content (e.g., user input captions) onthe captured image for publication as an ephemeral message 502. Theinterface engine 625 is configured to receive the image from the contentengine 620 and publish the image and the overlay content as an ephemeralmessage 502 on a social media network site, as discussed above.

FIG. 7 shows an example flow diagram of a method 700 for implementinggeo-parameter based content distribution, according to some exampleembodiments. At operation 705, the map engine 605 displays a map on thedisplay device of the client device 102. For example, the client device102 may use a GPS sensor to determine that the client device 102 islocated near a city park. Then at operation 705 the map displayed may bea map of the park and the surrounding streets, and may include a useravatar showing a user location of a user of the client device 102. Atoperation 710, the geolocation engine 610 determines the geographicphysical location of the client device 102. The physical location datamay be previously stored location data used to display the map atoperation 705.

At operation 715, the icon engine 615 determines icon settings based onicon metadata. The icon metadata describes settings that must besatisfied to unlock (e.g., access, display) content associated with agiven icon. For example, a given icon may have icon metadata specifyingthat the user must be viewing the map at zoom level 9 out of 10 (where0/10 is not zoomed in and 10/10 is max zoom), and further that theclient device 102 must be within one or more pre-set distances of theicon coordinates for the icon overlay content to be unlocked. Thepre-set distances may include a geo-fence distance and an iconvisibility distance, according to some example embodiments. Thegeo-fence distance is a threshold distance that must be met to unlockcontent associated with a given icon. The geo-fence distance may be acircle set by a radius, or an arbitrary polygon shape set by one or morevertices. The icon visibility distance is a threshold distance that mustbe met for a given icon to be displayed on the map.

In some example embodiments, upon the messaging client application 104being initiated on the client device 102, e.g., the icon engine 615transmits a request to the application server 112 requesting icons thatare near the current physical location of the client device 102. Forexample, the icon engine 615 sends the icon system 150 the latitude andlongitude of the client device 102 (e.g., according to GPS sensor dataof the client device 102). The icon engine 615 may further request allicons within some distance, e.g., 20 miles, of the client device 102.The icon system 150 then accesses the database 120 for the requested setof icons and sends the icons to the icon engine 615. In some exampleembodiments, only icon metadata is sent, including data such as iconcoordinates, an icon thumbnail, and the zoom level and distancerequirements discussed above. That is, in some embodiments, only theicon data is returned and the actual overlay content is kept on thedatabase 120 until it is unlocked or otherwise requested. By sendingicon data instead of icon data and overlay content, network resourcesare conserved. In some example embodiments, the overlay content is sentwith the icon data when the client device 102 is connected to a Wi-Finetwork and does not need to use cellular data of the client device 102to download the overlay content.

At operation 725, the map engine 605 displays an icon at iconcoordinates on the map based on the icon settings being satisfied. Forexample, assume that at operation 725, the client device 102 issufficiently close to the icon coordinates to satisfy the iconvisibility distance and the current zoom level further satisfies arequired zoom level setting for that icon.

At operation 730, the map engine 605 receives selection of the icondisplayed on the map. For example, the user of the client device 102taps on a touchscreen over the icon to select the icon.

At operation 735, the content engine 620 displays overlay content on thedisplay device of the client device 102. For example, at operation 715,the icon engine 615 determined that the client device 102 meets thegeo-fence distance setting and unlocks access to the content for thaticon. Then, at operation 735, the content engine 620 accesses thecontent for the icon and displays it on the client device 102. In someexample embodiments, the content engine 620 first transmits a request tothe icon system 150 for the unlocked content, then displays the contentupon receiving it from the icon system 150.

At operation 740, the interface engine 625 publishes the image and theoverlay content as an ephemeral message on a social media network site.For example, the interface engine 625 may capture an image using animage sensor of the client device 102, and then overlay the newlyunlocked content on the image and publish the image and overlay contentas a modified image in an ephemeral message 502 at operation 740.

FIG. 8 shows an example finite state machine (FSM) architecture 800 forconfiguration of the icon engine 615 based on icon settings, accordingto some example embodiments. The icon engine 615 controls whether agiven icon is displayed and whether the content of the given icon isaccessible (e.g., can be unlocked and displayed). The various iconparameters being satisfied or unsatisfied enable the icon engine 615 tobe automatically configured in different states. In the FSM architecture800 there are four states. In the first state 805, no icon is displayedon the map, and the corresponding icon content is locked or otherwisenot displayable. For example, the icon engine 615 is in the first state805 when the client device 102 is outside the icon's geo-fence andeither the zoom level or the icon visibility distance is not satisfied.

In the second state 810, an icon is displayed but the icon content islocked or otherwise not displayable. For example, the icon engine 615 isin the second state 810 when the client device 102 is outside the icon'sgeo-fence (thereby keeping the content locked), but the icon is stilldisplayed due to the icon visibility distance and the zoom level beingsatisfied.

In the third state 815, no icon is displayed on the map but the contentassociated with the icon is unlocked (e.g., accessible and displayable).For example, the icon engine 615 is in the third state 815 when theclient device 102 is within the geo-fence of the icon but the zoom levelis not met. In that example, the content engine 620 may still access andpre-download the unlocked content, e.g., from the icon system 150. Inanother example, the icon engine 615 is in the third state 815 when theclient device 102 is within the geo-fence of the icon but not within theicon visibility distance (e.g., the icon visibility distance isenveloped by the geo-fence area).

In the fourth state 820, an icon is displayed on the map and the contentis unlocked. For example, the icon engine 615 is in the fourth statewhen the client device 102 is within the geo-fence for the icon and thezoom level parameter and the icon visibility parameter are met.

When the icon engine 615 is in a given state, it stays in the givenstate upon determining that the input conditions are the same. Forexample, if in the first state 805, the icon engine 615 may periodicallycheck whether icon parameters have changed (e.g., via distance changesor zoom level changes), and if the icon parameters are unchanged, theicon engine 615 remains in the first state 805, as indicated by a looparrow 825. Likewise, if in the second state 810, the icon engine 615 mayperiodically check whether icon parameters have changed (e.g., viadistance changes or zoom level changes), and if the icon parameters areunchanged, the icon engine 615 remains in the second state 810, asindicated by a loop arrow 830. Likewise, if in the third state 815, theicon engine 615 may periodically check whether icon parameters havechanged (e.g., via distance changes or zoom level changes), and if theicon parameters are unchanged, the icon engine 615 remains in the thirdstate 815, as indicated by a loop arrow 835. Likewise, if in the fourthstate 820, the icon engine 615 may periodically check whether iconparameters have changed (e.g., via distance changes or zoom levelchanges), and if the icon parameters are unchanged, the icon engine 615remains in the fourth state 820, as indicated by a loop arrow 840.

Further, the icon engine 615 may transition states in response toconditions being input into the icon engine 615 changing. For example,the icon engine 615 may transition from the first state 805 to thesecond state 810, and vice versa, using a transition 845 (e.g., inresponse to a zoom level parameter being satisfied or unsatisfied).Likewise, the icon engine 615 may transition from the first state 805 tothe fourth state 820, and vice versa, using a transition 870 (e.g., inresponse to the geo-fence parameter and zoom level parameter beingsatisfied or unsatisfied). Likewise, the icon engine 615 may transitionfrom the first state 805 to the third state 815, and vice versa, using atransition 860 (e.g., in response to a geo-fence parameter beingsatisfied or unsatisfied). Likewise, the icon engine 615 may transitionfrom the second state 810 to the third state 815, and vice versa, usinga transition 865 (e.g., in response to a zoom level parameter beingsatisfied or unsatisfied, and the geo-fence parameter being satisfied orunsatisfied). Likewise, the icon engine 615 may transition from thesecond state 810 to the fourth state 820, and vice versa, using atransition 850 (e.g., in response to the geo-fence parameter beingsatisfied or unsatisfied). Likewise, the icon engine 615 may transitionfrom the third state 815 to the fourth state 820, and vice versa, usinga transition 855 (e.g., in response to a zoom level parameter or iconvisibility parameter being satisfied or unsatisfied).

In some example embodiments, using a polling approach, the icon engine615 is configured to periodically check whether conditions (e.g.,distances, zoom level) have changed. In other embodiments, the iconengine 615 is informed of changes using interrupts or automaticnotification approaches, such as by key-value observing (KVO).

Further, although three icon parameters are discussed above, i.e., anicon geo-fence, an icon visibility distance, and a zoom level, it willbe appreciated that in some example embodiments two of the parametersare implemented instead of all three. For example, the icon engine 615may implement the FSM architecture 800 using the geo-fence parameter andthe zoom level setting parameter.

FIG. 9 shows example icon settings 900, according to some exampleembodiments. In some example embodiments, the example icon settings 900are displayed on the display device of the client device 102. Forexample, the icon settings 900 can be displayed as overlay elements on amap. In some example embodiments, time example icon settings 900 are notdisplayed on the display device of the client device 102, but rather theicon engine 615 tracks the parameters, displays an icon 905, and thenlocks or unlocks content based on the parameters satisfying the settingsper icon metadata.

In FIG. 9, an icon 905 has been placed at icon coordinates (e.g.,latitude and longitude) on a map (not depicted). A geo-fence 910 havinga pre-specified geo-fence distance circumscribes the icon 905. In someexample embodiments, the geo-fence 910 is a circle having a givenradius. In other example embodiments, as illustrated in FIG. 9, thegeo-fence 910 is delineated by specifying a number of vertices thatcreate a polygon circumscribing the icon 905. The vertices can bespecified and stored in the icon metadata by an administrator or creatorof the icon 905 and/or overlay content, according to some exampleembodiments.

In the example shown in FIG. 9, the geo-fence 910 is a pentagon havingnon-uniform sides. Further surrounding the icon 905 is an iconvisibility area 915, denoted by the broken-line circle. The iconvisibility area 915 sets an area (e.g., inside the circle) in which theclient device 102 must be physically located for the icon 905 to appearon a map displayed on the client device 102. In some exampleembodiments, the icon 905 may also be displayed and/or content may beunlocked based on a zoom level setting being satisfied, as discussed infurther detail with reference to FIGS. 11A and 11B below.

In the example of FIG. 9, a user 920 (who is holding a client device,not depicted in FIG. 9) is outside the geo-fence 910 and outside theicon visibility area 915. As such, the user 920 will not see the icon905, as he or she is outside the icon visibility area 915, and furtherwill not be able to unlock any content associated with the icon 905,because the user 920 is outside the geo-fence 910. Another user 925 (whois holding another client device, not depicted in FIG. 9) is inside theicon visibility area 915 but outside the geo-fence 910. As such, theuser 925 will be able to see the icon 905 displayed on his or her clientdevice but will not be able to unlock the content associated with theicon 905 because the user 925 is outside the geo-fence 910. Further, auser 930 (who is holding another client device, not depicted in FIG. 9)is located inside the geo-fence 910 and further inside the iconvisibility area 915. As such, the user 930 will be able to see the icon905 because the user 930 is within the icon visibility area 915;further, the user 930 will be able to unlock the content associated withthe icon 905 because the user 930 is within the geo-fence 910. Althoughthe users 920, 925, and 930 are at different physical distances from theicon 905, in some example embodiments, regardless of the distanceparameters, the zoom level setting must still be met for the icon 905 tobe displayed on the map. Further, according to some example embodiments,the zoom level must be met for the content associated with the icon 905to be unlocked, whether or not the user is within the geo-fence 910.

FIG. 10A shows an example map 1000 being displayed on a display deviceof the client device 102, according to some example embodiments. In FIG.10A, a user avatar 1010 is displayed at the physical location of theclient device 102. Further, an icon 1005 is displayed on the map 1000 aticon coordinates. As illustrated, the icon 1005 comprises a thumbnailpreviewing the content that is potentially unlockable.

FIG. 10B shows an updated map 1015, according to some exampleembodiments. In FIG. 10B, the user (not depicted) has selected the icon1005 by tapping on the icon 1005 on the display device of the clientdevice 102. In the example illustrated, the zoom level is met and thevisibility radius is met because the icon 1005 is visible. However,after selecting the icon 1005, the user is prompted with a notification1020 that notifies the user that he or she should travel closer to theicon coordinates to unlock content. Thus, the user is outside thegeo-fence for the icon 1005.

FIG. 10C shows an updated map 1025, according to some exampleembodiments. In FIG. 10C, the user avatar 1010 has been updated to a newposition based on the user (not depicted) moving physically closer tothe icon coordinates. Once the user is within the geo-fence of the icon1005, a notification 1030 is displayed on the map 1025 that notifies theuser that he or she can execute the newly unlocked content associatedwith the icon 1005, e.g., by selecting an “OPEN” user interface buttonwithin the notification 1030.

FIG. 10D shows an example user interface 1035 of a live image andunlocked content, according to some example embodiments. In FIG. 10D,upon the user (not depicted) unlocking the content via the notification1030 (see FIG. 10C), the display device of the client device 102 shows alive feed 1040 of the client device 102 (e.g., a live video feedgenerated by an image sensor of the client device 102). In the exampleillustrated, the live feed 1040 displays a park environment in which theclient device 102 is located. Further, newly unlocked overlay content1045 (e.g., a three-dimensional dancing hotdog with floating musicalnotes) is displayed on the live feed 1040. The user can select a button1050 to capture or otherwise sample an image from the live feed 1040with the overlay content 1045 shown. The captured image and content canbe published as an ephemeral message 502, according to some exampleembodiments.

FIG. 11A shows an example user interface 1100 at a first zoom setting,according to some example embodiments. In FIG. 11A, the user interface1100 is displaying a map at the first zoom setting. As illustrated, theicon is not depicted because the zoom level of the icon (e.g., as set bythe icon settings metadata) has not been met.

FIG. 11B shows an example user interface 1105 at a second zoom setting,according to some example embodiments. In FIG. 11B, the user interface1105 is displaying a map at the second zoom setting in response to theuser zooming in on a section of the map (e.g., using a pinch and zoomgesture on the touchscreen of the client device 102). In response to thesecond zoom setting, an icon 1110 is displayed on the map.

FIG. 12 is a block diagram illustrating an example software architecture1206, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 12 is a non-limiting example of asoftware architecture, and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 1206 may execute on hardwaresuch as a machine 1300 of FIG. 13 that includes, among other things,processors, memory, and I/O components. A representative hardware layer1252 is illustrated and can represent, for example, the machine 1300 ofFIG. 13. The representative hardware layer 1252 includes a processingunit 1254 having associated executable instructions 1204. The executableinstructions 1204 represent the executable instructions of the softwarearchitecture 1206, including implementation of the methods, components,and so forth described herein. The hardware layer 1252 also includes amemory/storage 1256, which also has the executable instructions 1204.The hardware layer 1252 may also comprise other hardware 1258.

In the example architecture of FIG. 12, the software architecture 1206may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 1206may include layers such as an operating system 1202, libraries 1220,frameworks/middleware 1218, applications 1216, and a presentation layer1214. Operationally, the applications 1216 and/or other componentswithin the layers may invoke API calls 1208 through the software stackand receive a response in the form of messages 1212. The layersillustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile orspecial-purpose operating systems may not provide aframeworks/middleware 1218, while others may provide such a layer. Othersoftware architectures may include additional or different layers.

The operating system 1202 may manage hardware resources and providecommon services. The operating system 1202 may include, for example, akernel 1222, services 1224, and drivers 1226. The kernel 1222 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 1222 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1224 may provideother common services for the other software layers. The drivers 1226are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1226 include display drivers; cameradrivers, Bluetooth® drivers, flash memory drivers, serial communicationdrivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers,audio drivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 1220 provide a common infrastructure that is used by theapplications 1216 and/or other components and/or layers. The libraries1220 provide functionality that allows other software components toperform tasks in an easier fashion than by interfacing directly with theunderlying operating system 1202 functionality (e.g., kernel 1222,services 1224, and/or drivers 1226). The libraries 1220 may includesystem libraries 1244 (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematical functions, and the like. In addition, thelibraries 1220 may include API libraries 1246 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia formats such as MPEG-4, H.264, MP3, AAC, AMR, JPG, or PNG),graphics libraries (e.g., an OpenGL framework that may be used to render2D and 3D graphic content on a display), database libraries (e.g.,SQLite that may provide various relational database functions), weblibraries (e.g., WebKit that may provide web browsing functionality),and the like. The libraries 1220 may also include a wide variety ofother libraries 1248 to provide many other APIs to the applications 1216and other software components/modules.

The frameworks/middleware 1218 provide a higher-level commoninfrastructure that may be used by the applications 1216 and/or othersoftware components/modules. For example, the frameworks/middleware 1218may provide various graphic user interface (GUI) functions, high-levelresource management, high-level location services, and so forth. Theframeworks/middleware 1218 may provide a broad spectrum of other APIsthat may be utilized by the applications 1216 and/or other softwarecomponents/modules, some of which may be specific to a particularoperating system 1202 or platform.

The applications 1216 include built-in applications 1238 and/orthird-party applications 1240. Examples of representative built-inapplications 1238 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. The third-party applications 1240 may includean application developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platform,and may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 1240 may invoke the API calls 1208 provided bythe mobile operating system (such as the operating system 1202) tofacilitate functionality described herein.

The applications 1216 may use built-in operating system functions (e.g.,kernel 1222, services 1224, and/or drivers 1226), libraries 1220, andframeworks/middleware 1218 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systems,interactions with a user may occur through a presentation layer, such asthe presentation layer 1214. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 13 is a block diagram illustrating components of a machine 1300,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 13 shows a diagrammatic representation of the machine1300 in the example form of a computer system, within which instructions1316 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1300 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 1316 may be used to implement modules or componentsdescribed herein. The instructions 1316 transform the general,non-programmed machine 1300 into a particular machine 1300 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1300 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1300 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1300 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smartphone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 1316, sequentially or otherwise, that specify actions to betaken by the machine 1300. Further, while only a single machine 1300 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 1316 to perform any one or more of the methodologiesdiscussed herein.

The machine 1300 may include processors 1310, memory/storage 1330, andI/O components 1350, which may be configured to communicate with eachother such as via a bus 1302. The memory/storage 1330 may include amemory 1332, such as a main memory, or other memory storage, and astorage unit 1336, both accessible to the processors 1310 such as viathe bus 1302. The storage unit 1336 and memory 1332 store theinstructions 1316 embodying any one or more of the methodologies orfunctions described herein. The instructions 1316 may also reside,completely or partially, within the memory 1332, within the storage unit1336, within at least one of the processors 1310 (e.g., within theprocessor cache memory accessible to processors 1312 or 1314), or anysuitable combination thereof, during execution thereof by the machine1300. Accordingly, the memory 1332, the storage unit 1336, and thememory of the processors 1310 are examples of machine-readable media.

The I/O components 1350 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1350 that are included in a particular machine 1300 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 1350 may include many other components that are not shown inFIG. 13. The I/O components 1350 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various example embodiments, the I/O components 1350may include output components 1352 and input components 1354. The outputcomponents 1352 may include visual components (e.g., a display such as aplasma display panel (PDP), a light-emitting diode (LED) display, aliquid-crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1354 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point-based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstruments), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1350 may includebiometric components 1356, motion components 1358, environmentcomponents 1360, or position components 1362 among a wide array of othercomponents. For example, the biometric components 1356 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram-basedidentification), and the like. The motion components 1358 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environment components 1360 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gassensors to detect concentrations of hazardous gases for safety or tomeasure pollutants in the atmosphere), or other components that mayprovide indications, measurements, or signals corresponding to asurrounding physical environment. The position components 1362 mayinclude location sensor components (e.g., a OPS receiver component),altitude sensor components (e.g., altimeters or barometers that detectair pressure from which altitude may be derived), orientation sensorcomponents (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1350 may include communication components 1364operable to couple the machine 1300 to a network 1380 or devices 1370via a coupling 1382 and a coupling 1372, respectively. For example, thecommunication components 1364 may include a network interface componentor other suitable device to interface with the network 1380. In furtherexamples, the communication components 1364 may include wiredcommunication components, wireless communication components, cellularcommunication components, near field communication (NFC) components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components to provide communication via othermodalities. The devices 1370 may be another machine or any of a widevariety of peripheral devices (e.g., a peripheral device coupled via aUSB).

Moreover, the communication components 1364 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1364 may include radio frequency identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional barcodes such as Universal Product Code (UPC) barcode,multi-dimensional barcodes such as Quick Response (QR) code, Aztec code,Data Matrix, Dataglyph, MaxiCode, PDF418, Ultra Code, UCC RSS-2Dbarcode, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1364, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

Glossary

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying instructions 1316 forexecution by the machine 1300, and includes digital or analogcommunications signals or other intangible media to facilitatecommunication of such instructions 1316. Instructions 1316 may betransmitted or received over the network 1380 using a transmissionmedium via a network interface device and using any one of a number ofwell-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine 1300 thatinterfaces to a network 1380 to obtain resources from one or more serversystems or other client devices 102. A client device 102 may be, but isnot limited to, a mobile phone, desktop computer, laptop, PDA,smartphone, tablet, ultrabook, netbook, multi-processor system,microprocessor-based or programmable consumer electronics system, gameconsole, set-top box, or any other communication device that a user mayuse to access a network 1380.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network 1380 that may be an ad hoc network, an intranet, anextranet, a virtual private network (VPN), a local area network (LAN), awireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), the Internet, a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), aplain old telephone service (POTS) network, a cellular telephonenetwork, a wireless network, a Wi-Fi® network, another type of network,or a combination of two or more such networks. For example, a network ora portion of a network 1380 may include a wireless or cellular networkand the coupling 1382 may be a Code Division Multiple Access (CDMA)connection, a Global System for Mobile communications (GSM) connection,or another type of cellular or wireless coupling. In this example, thecoupling may implement any of a variety of types of data transfertechnology, such as Single Carrier Radio Transmission Technology(1×RTT), Evolution-Data. Optimized (EVDO) technology, General PacketRadio Service (GPRS) technology, Enhanced Data rates for GSM Evolution(EDGE) technology, third. Generation Partnership Project (3GPP)including 3G, fourth generation wireless (4G) networks, Universal MobileTelecommunications System (UMTS), High-Speed Packet Access (HSPA),Worldwide Interoperability for Microwave Access (WiMAX), Long-TermEvolution (LTE) standard, others defined by various standard-settingorganizations, other long-range protocols, or other data transfertechnology.

“EMPHEMERAL MESSAGE” in this context refers to a message 400 that isaccessible for a time-limited duration. An ephemeral message 502 may bea text, an image, a video, and the like. The access time for theephemeral message 502 may be set by the message sender. Alternatively,the access time may be a default setting or a setting specified by therecipient. Regardless of the setting technique, the message 400 istransitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, adevice, or other tangible media able to store instructions 1316 and datatemporarily or permanently and may include, but is not limited to,random-access memory (RAM), read-only memory (ROM), buffer memory, flashmemory, optical media, magnetic media, cache memory, other types ofstorage (e.g., erasable programmable read-only memory (EPROM)), and/orany suitable combination thereof. The term “machine-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions 1316. The term “machine-readable medium”shall also be taken to include any medium, or combination of multiplemedia, that is capable of storing instructions 1316 (e.g., code) forexecution by a machine 1300, such that the instructions 1316, whenexecuted by one or more processors 1310 of the machine 1300, cause themachine 1300 to perform any one or more of the methodologies describedherein. Accordingly, a “machine-readable medium” refers to a singlestorage apparatus or device, as well as “cloud-based” storage systems orstorage networks that include multiple storage apparatus or devices. Theterm “machine-readable medium” excludes signals per se.

“COMPONENT” in this context refers to a device, a physical entity, orlogic having boundaries defined by function or subroutine calls, branchpoints, APIs, or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor 1312 ora group of processors 1310) may be configured by software (e.g., anapplication or application portion) as a hardware component thatoperates to perform certain operations as described herein. A hardwarecomponent may also be implemented mechanically, electronically, or anysuitable combination thereof. For example, a hardware component mayinclude dedicated circuitry or logic that is permanently configured toperform certain operations. A hardware component may be aspecial-purpose processor, such as a field-programmable gate array(FPGA) or an application-specific integrated circuit (ASIC). A hardwarecomponent may also include programmable logic or circuitry that istemporarily configured by software to perform certain operations. Forexample, a hardware component may include software executed by ageneral-purpose processor or other programmable processor. Onceconfigured by such software, hardware components become specificmachines (or specific components of a machine 1300) uniquely tailored toperform the configured functions and are no longer general-purposeprocessors 1310. It will be appreciated that the decision to implement ahardware component mechanically, in dedicated and permanently configuredcircuitry, or in temporarily configured circuitry (e.g., configured bysoftware) may be driven by cost and time considerations. Accordingly,the phrase “hardware component” (or “hardware-implemented component”)should be understood to encompass a tangible entity, be that an entitythat is physically, constructed, permanently configured (e.g.,hardwired), or temporarily configured (e.g., programmed) to operate in acertain manner or to perform certain operations described herein.

Considering embodiments in which hardware components are temporarilyconfigured (e.g., programmed), each of the hardware components need notbe configured or instantiated at any one instance in time. For example,where a hardware component comprises a general-purpose processor 1312configured by software to become a special-purpose processor, thegeneral-purpose processor 1312 may be configured as respectivelydifferent special-purpose processors (e.g., comprising differenthardware components) at different times. Software accordingly configuresa particular processor 1312 or processors 1310, for example, toconstitute a particular hardware component at one instance of time andto constitute a different hardware component at a different instance oftime.

Hardware components can provide information to, and receive informationfrom, other hardware components. Accordingly; the described hardwarecomponents may be regarded as being communicatively coupled. Wheremultiple hardware components exist contemporaneously, communications maybe achieved through signal transmission (e.g., over appropriate circuitsand buses) between or among two or more of the hardware components. Inembodiments in which multiple hardware components are configured orinstantiated at different times, communications between or among suchhardware components may be achieved, for example, through the storageand retrieval of information in memory structures to which the multiplehardware components have access. For example, one hardware component mayperform an operation and store the output of that operation in a memorydevice to which it is communicatively coupled. A further hardwarecomponent may then, at a later time, access the memory device toretrieve and process the stored output. Hardware components may alsoinitiate communications with input or output devices, and can operate ona resource (e.g., a collection of information).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors 1310 that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors 1310 may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors1310. Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor 1312 or processors1310 being an example of hardware. For example, at least some of theoperations of a method may be performed by one or more processors 1310or processor-implemented components. Moreover, the one or moreprocessors 1310 may also operate to support performance of the relevantoperations in a “cloud computing” environment or as a “software as aservice” (SaaS). For example, at least some of the operations may beperformed by a group of computers (as examples of machines 1300including processors 1310), with these operations being accessible via anetwork 1380 (e.g., the Internet) and via one or more appropriateinterfaces (e.g., an API). The performance of certain of the operationsmay be distributed among the processors 1310, not only residing within asingle machine 1300, but deployed across a number of machines 1300. Insome example embodiments, the processors 1310 or processor-implementedcomponents may be located in a single geographic location (e.g., withina home environment, an office environment, or a server farm). In otherexample embodiments, the processors 1310 or processor-implementedcomponents may be distributed across a number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor1312) that manipulates data values according to control signals (e.g.,“commands,” “op codes,” “machine code,” etc.) and which producescorresponding output signals that are applied to operate a machine 1300.A processor may, for example, be a central processing unit (CPU), areduced instruction set computing (RISC) processor; a complexinstruction set computing (CISC) processor, a graphics processing unit(GPU), a digital signal processor (DSP), an ASIC, a radio-frequencyintegrated circuit (RFIC), or any combination thereof. A processor 1310may further be a multi-core processor 1310 having two or moreindependent processors 1312, 1314 (sometimes referred to as “cores”)that may execute instructions 1316 contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters orencoded information identifying when a certain event occurred, forexample giving date and time of day, sometimes accurate to a smallfraction of a second.

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described above and in the drawings that form a part of thisdocument: Copyright 2017, SNAP INC., All Rights Reserved.

What is claimed is:
 1. A method comprising: displaying a map on adisplay device of a client device; displaying, within the map, a clientdevice icon indicating a geographic location of the client device and acontent icon indicating another geographic location on the map, thecontent icon encircled on the map by a visual perimeter element of anunlock area near the another geographic location that the client devicemust be located in order to unlock content associated with the contenticon; receiving, by the client device, selection of the content icon tounlock the content associated with the content icon; in response to theselection of the content icon, display a prompt to move the clientdevice within the unlock area of the visual perimeter element;displaying, on the client device, an updated map displaying the clientdevice icon at a new geographic location that is within the unlock areaof the visual perimeter element; receiving, by the client device,another selection of the content icon to unlock the content associatedwith the content icon; and in response to the another selection and theclient device being in the unlock area of the visual perimeter element,displaying the content associated with the content icon on the displaydevice of the client device.
 2. The method of claim 1, wherein the iconis displayed based at least in part on the location data of the clientdevice being within a pre-specified icon visibility distance that isdifferent than the pre-specified geo-fence distance.
 3. The method ofclaim 1, further comprising: receiving, on the client device, selectionof the icon displayed on the map, wherein the at least one item ofoverlay content is displayed in response to receiving the selection. 4.The method of claim 3, further comprising: in response to receiving theselection, transmitting a request over a network to a server for the atleast one item of overlay content.
 5. The method of claim 1, wherein theicon is a thumbnail displaying at least a portion of the overlaycontent.
 6. The method of claim 1, wherein the overlay content is userinterface content configured for overlay on one or more images captured,using the client device while located within the pre-specified geo-fencedistance of the icon coordinates.
 7. The method of claim 1, furthercomprising: determining that the location data of the client device iswithin another pre-specified geo-fence distance of additional iconcoordinates of an additional icon; determining that the map is notdisplayed at an additional pre-specified zoom level of the additionalicon; and requesting, from a server, additional overlay contentpre-associated with the additional icon while not displaying theadditional icon on the map.
 8. The method of claim 2, wherein the iconis displayed only if the map is displayed at the pre-specified zoomlevel on the client device and the client device is within thepre-specified icon visibility according to the location data of theclient device.
 9. The method of claim 8, wherein the at least one itemof overlay content is accessible only if the client device is within thepre-specified geo-fence distance according to the location data of theclient device.
 10. The method of claim 1, wherein the network sensor isa Global Positioning System (GPS) sensor and the location data is GPSdata.
 11. The method of claim 1, wherein the network sensor is anInternet Protocol (IP) sensor, and the location data includes an IPaddress.